fix(mcp): scope HF bearer token to HuggingFace endpoints only - #323

Problem

ToolRouter.__init__ (agent/core/tools.py) injects Authorization: Bearer <hf_token> into the headers of every configured MCP server:

for name, server in mcp_servers.items():
    data = server.model_dump()
    if hf_token:
        data.setdefault("headers", {})["Authorization"] = f"Bearer {hf_token}"
    mcp_servers_payload[name] = data

Two issues:

1. Credential leak — the user's HF token is sent to every MCP server they configure, including unrelated/third-party servers that have no business seeing it.
2. Breaks auth-enforcing servers — a server that grants a default identity to unauthenticated localhost callers (e.g. a self-hosted data-gateway) instead receives an unrecognized hf_... bearer and rejects every tool call. In my setup a local gateway returned invalid_token: bearer token not recognized on all calls; removing the stray header let it fall back to its default localhost identity and work.

Fix

Only attach the HF bearer when the server URL is a HuggingFace endpoint, matched on the parsed hostname (huggingface.co or a subdomain such as router.huggingface.co) rather than a substring — so lookalike hosts like huggingface.co.evil.com don't match. Stdio servers (no URL) and all non-HF remotes now receive no Authorization header.

if hf_token and _is_hf_endpoint(data.get("url")):
    data.setdefault("headers", {})["Authorization"] = f"Bearer {hf_token}"

The default hf-mcp-server (https://huggingface.co/mcp?login) still receives the token unchanged.

Verification

_is_hf_endpoint behavior:

Confirmed end-to-end: with the default hf-mcp-server plus a local data-gateway MCP, tool calls to both succeed after the change (before, the data-gateway rejected every call with invalid_token).

🤖 Generated with Claude Code